6.2.0 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
- Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-3: Specifying Statements

The Appearance Number


Many of the characteristic-type statements allow you to specify which iteration, or appearance number, is to be affected by the statement. An appearance number is applicable only when a field appears more than once on an image. For example:

This example indicates that the system should make the CUSTOMER NAME field in the TAR application appear as inverse on the terminal for the second appearance only of this field on the image. The text, AT APPEARANCE #, is automatically provided by the ILF as part of this statement?s format template.

Occurrence vs Appearance. A field may appear on an image multiple times. A field with an Occurrence number is unique onto itself. If there are two fields on an image, WORK ADDRESS OCC 001 and WORK ADDRESS OCC 002 and the second occurrence value is changed, Appx will recognize that change and display the new value. If, however, WORK ADDRESS (no OCC) is on an image more than once you must identify these instances with the Appearance parameter.

Application Design Manual                                         "Powered by Appx Software"

1365

©2006-2023 By APPX Software, Inc. All Rights Reserved